Revision: arch--lord--1.0--patch-11
Archive: lord@regexps.com--2002
Creator: Tom Lord <lord@regexps.com>
Date: Mon Jan  7 17:23:27 PST 2002
Standard-date: 2002-01-07
Summary: new command: `new-on-branch' and ChangeLog re-org
Keywords: 
New-files: {arch}/arch/arch--lord/arch--lord--1.0/lord@regexps.com--2002/patch-log/patch-11
  patch-logs/new-on-branch.sh
Renamed-files: ChangeLog.d/lord@regexps.com--2001Q4/ChangeLog.devo ChangeLog.d/lord@regexps.com--2001Q4/ChangeLog.devo--1.0
  ChangeLog.d/lord@regexps.com--2002/ChangeLog ChangeLog.d/lord@regexps.com--2002/ChangeLog.lord--1.0
Modified-files: ChangeLog
  ChangeLog.d/lord@regexps.com--2002/ChangeLog.lord--1.0
  archive-transactions/commit.sh patch-logs/Help.list.in
New-patches: lord@regexps.com--2002/arch--lord--1.0--patch-11

Name ChangeLogs by branch.  Use tagged ChangeLogs.

Fixed a bug that caused `commit' to fail when a tagged ChangeLog has
been renamed.

`new-on-branch' reports a list of patches found in a project tree, but
apparently not-yet merged into a particular branch.

This is quite useful when generating log entries for a merge:


	% arch new-on-branch MERGED-INTO-VERSION
	...list of patches...

so the output of:

	% arch new-on-branch --reverse MERGED-INTO-VERSION \
	  | xargs -r -n 1 arch log-ls --summary --full

is easily editted into a reasonable log message, especially if you 
organize changelogs as they are in this tree.



